chore(release): v0.12.2#1141
Merged
danielmeppiel merged 1 commit intomainfrom May 5, 2026
Merged
Conversation
Roll forward the four PRs merged since v0.12.1: - #1137 feat(audit): default-on integration drift detection - #1135 fix(deps): subdir-agnostic bare cache (parallel sparse-checkout race) also resolves duplicate report #1140 (ADO sub-path manifestation) - #1129 docs: first-package guide accuracy (includes: auto, skill paths) - #1127 docs: APM's role for skills, plugins-as-packages, ADO sub-paths Bump pyproject.toml + uv.lock 0.12.1 -> 0.12.2 and convert the Unreleased CHANGELOG block into the 0.12.2 section, with a single 'so what' line per merged PR per the changelog contract. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This is a release-cut PR for v0.12.2. It bumps the package metadata to the new patch version and moves the four merged changes since v0.12.1 into a new released section of CHANGELOG.md, covering the drift-detection improvement, the subdirectory install race fix reported again on ADO, and two documentation updates.
Changes:
- Bump the project version from
0.12.1to0.12.2in packaging metadata. - Update
uv.lockso the editableapm-clipackage version matches the release. - Convert the current unreleased changelog entries into a new
0.12.2release section with four shipped PR summaries.
Show a summary per file
| File | Description |
|---|---|
pyproject.toml |
Updates the published package version to 0.12.2. |
uv.lock |
Syncs the lockfile's editable apm-cli entry to 0.12.2. |
CHANGELOG.md |
Creates the 0.12.2 release section and records the four merged PRs in the changelog. |
Copilot's findings
Comments suppressed due to low confidence (1)
CHANGELOG.md:23
- These entries also diverge from
.github/instructions/changelog.instructions.md:18-20, which requires a single concise line per PR ending with(#PR_NUMBER). Keeping the docs PR bullets in the same one-line format matters here because this release section is what gets published verbatim.
- **Docs: `first-package` guide accuracy.** Clarifies how `includes: auto` actually behaves and corrects the skill deployment paths so a newcomer's first package matches what `apm install` writes to disk. (#1129)
- **Docs: APM's role for skills, plugins-as-packages, ADO sub-paths.** Six user-surfaced doc gaps closed in one pass -- unifies the "plugin == package" framing, adds ADO sub-path install examples, and states the current stability posture so users stop guessing from release notes. (#1127)
- Files reviewed: 2/3 changed files
- Comments generated: 2
|
|
||
| ### Added | ||
|
|
||
| - **`apm audit` now catches forgotten installs and hand-edits by default.** No more shipping stale `.github/instructions/` because someone forgot to re-run `apm install`, no more silent hand-edits to regenerated content. Opt out with `--no-drift`. See the [Drift Detection guide](https://danielmeppiel.github.io/awd-cli/guides/drift-detection/). (#1137, closes #1071, supersedes scope of #898) |
Comment on lines
+18
to
+22
| - **Parallel subdir install race.** `apm install` no longer intermittently fails with `RuntimeError: Subdirectory '<path>' not found in repository` when multiple dependencies (including ADO sub-path deps) resolve to different subdirectories of the same `repo@ref`. The shared clone cache now stores subdir-agnostic bare clones and each consumer materializes its own working tree (mirrors the WS3 `GitCache` pattern). (#1135, fixes #1126, fixes #1140) | ||
|
|
||
| ### Changed | ||
|
|
||
| - **Docs: `first-package` guide accuracy.** Clarifies how `includes: auto` actually behaves and corrects the skill deployment paths so a newcomer's first package matches what `apm install` writes to disk. (#1129) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
Cut v0.12.2 -- a small patch release that ships the four PRs merged since v0.12.1, headlined by the parallel sub-path install race fix that was being re-reported by users on ADO (#1140).
What's in it
apm auditnow catches forgotten installs and hand-edits by default (--no-driftto opt out)repo@refno longer race -- subdir-agnostic bare cache + per-consumer materialization. Fixes #1126 and the duplicate ADO report #1140first-packageguide -- correctsincludes: autobehavior and skill deployment pathsEach PR gets exactly one "so what" line in
CHANGELOG.mdper the changelog contract.Mechanics
pyproject.toml:0.12.1->0.12.2uv.lock: re-locked (only theapm-clipackage version changes)CHANGELOG.md:[Unreleased]block converted to## [0.12.2] - 2026-05-05; [BUG] Can no longer depend on other skills etc in the same repo #1140 added to the fix(deps): subdir-agnostic bare cache fixes parallel sparse-checkout race (#1126) #1135 fix line; two new docs entries under### ChangedWhy now
#1140 lands the second user-visible report of the #1126 race in two days, both with the same
Subdirectory '...' not foundsymptom and the same "run install twice" workaround. The fix has been onmainsince #1135 merged; getting it tagged unblocks ADO sub-path users without asking them to build from source.Validation
uv run --extra dev ruff check src/ tests/ && uv run --extra dev ruff format --check src/ tests/(no source changes in this PR; onlypyproject.toml,uv.lock,CHANGELOG.md)v0.12.2is pushed after merge (per.github/instructions/cicd.instructions.md: onlyv*.*.*tags trigger the full release pipeline).Post-merge
v0.12.2onmainand push -- triggers build-release workflow.Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com